🚨 [security] Update sidekiq: 5.2.5 → 5.2.10 (patch)#313
Open
depfu[bot] wants to merge 1 commit intomasterfrom
Open
🚨 [security] Update sidekiq: 5.2.5 → 5.2.10 (patch)#313depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sidekiq (5.2.5 → 5.2.10) · Repo · Changelog
Release Notes
5.2.9 (from changelog)
5.2.8 (from changelog)
5.2.7 (from changelog)
5.2.6 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 55 commits:
Release for CVE and redis-rbBackport 7785ac1399f1b28992adb56055f6acd88fd1d956 (#5157)migrate "exists" to new Redis version and update to redis 4.2.0 (#5135)Fix build?Fix broken testAvoid redis-rb >= 4.2 due to `exists` API deprecation.bump, releaseAllow newer rack version due to directory traversal security bug (#4562)releaseFixes regression after refactoring (Closes #4456) (#4457)bumpLock Sidekiq 5 to Rack <2.1 to avoid breaking changes, #4440Fix Rails::VERSION check for sinatra and ActiveRecord (#4433)polishmove off traviscifixfixcirclecichanges, bumpre-establish Web UI test by stubbing time.now, #4149Update tests for #4149Revert "Allow tests to override enqueued_at", fixes #4149bump, releaseExplicitly signal that we handled an exception with a retry, fixes #4138 (#4141)Minor fixes to COMM-LICENSE (#4135)bump jruby to fix issue running test suiteFix broken build due to rails/rails#35611releaseAllow Sidekiq::Worker#set to be chainedFix heroku wait time, change it to 30 from 10 (#4117)flush redis so status is predictableRefactor sidekiqctl so it can be tested easilyFix various flaky tests due to process-wide data changesAllow tests to override enqueued_atoopsSwitch all tests to use Minitest::Spec for consistencyFormat latency (#4111)ent changeMerge branch 'master' of github.com:mperham/sidekiqadd back the dropdown css (#4103)ES localereleasescleanupBetter handling of malformed job arguments in payload, fixes #4095adapt to rails 5.2.2's draconian sqlite3 version requirementremove things which complicate the test suiteno longer necessarySimplify, prep for 6.0super fetch latencycleanup, #4089Rescue StandardErrors raised from exception's message (#4089)organization license -> limited licenseAdd clause for the Enterprise site licensechangesadd default queue latencyRelease Notes
2.2.5 (from changelog)
2.2.4 (from changelog)
2.2.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 47 commits:
changes, bumpFix argument forwarding in Ruby 2.7 (#149)update build status badge to use GitHub Workflow (#146)Mark truffleruby experimental in CI (#147)Migrate to GitHub Workflows (#145)Prep for releaseCI: add Ruby 3.0 (#144)Ruby 3.0: split positional/keyword args (#143)Allow restarting pool (#140)Add #138Add docs for ConnectionPool#thenImplement ConnectionPool#thenRemove `@key_count` from the thread when returning the connection to the poolAdd required_ruby_version to the GemspecMerge branch 'master' of github.com:mperham/connection_poolremove standard as it requires Ruby 2.4Comments use ConnectionPool::TimeoutErrorRejigger to remove errors.rbIntegrate standard gem, code formatting fixes, no functional changesMove wrapper into separate fileRejigger exceptions, fixes #130CI: Use openjdk11CI: refer to JRuby using rvm aliasCI: Run latest JRuby releaseREADME: Use API Redis.new in exampleRemoved explicitly declaration of thread library.Add ruby 2.7 to CICI: Use 2.6, 2.5, 2.4, jruby-9.2.8.0CI: Use latest patch versions of RubiesCI: Drop unused sudo: false directivemperham/connection_pool#113 expose pool from Wrapper (#114)bump jrubyInterrupt timing is implementation-specific (#112)fix jrubydoc failurechanges, cleanupmergefreshen up ruby matrixremove old jruby hacks, cleanup codeRemove monotonic clock hacksRemove wrapper for monotonic time (#109)Don't let threads die from exceptions in testsStricter casting of connection pool sizeEnsure size is integerpolishadd stats to READMEbumpSecurity Advisories 🚨
🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names
🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names
🚨 Directory traversal in Rack::Directory app bundled with Rack
🚨 Directory traversal in Rack::Directory app bundled with Rack
🚨 Possible information leak / session hijack vulnerability
Release Notes
2.2.2 (from changelog)
2.2.1 (from changelog)
2.2.0 (from changelog)
2.1.2 (from changelog)
2.1.1 (from changelog)
2.1.0 (from changelog)
2.0.8 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
2.1.0 (from changelog)
2.0.8.1 (from changelog)
2.0.8 (from changelog)
2.0.7 (from changelog)
2.0.6 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands